System, method and medium for certifying and accrediting requirements compliance

ABSTRACT

A computer-implemented system, method and medium for assessing the risk of and/or determining the suitability of a system to comply with at least one predefined standard, regulation and/or requirement. In at least some embodiments of the present invention, the method comprises the steps of: 1) gathering information pertaining to the system, 2) selecting one or more requirements with which the system is to comply; 3) testing the system against the requirements; 4) performing risk assessment of the failed test procedures, and 5) generating certification documentation based on an assessment of the first four elements.

RELATED APPLICATION

[0001] This application claims priority to application Ser. No.60/223,982, filed Aug. 9, 2000, entitled “Web Certification andAccreditation System, Method and Medium”, which is assigned to theassignee of this application. The disclosure of application Ser. No.60/223,982 is incorporated herein by reference.

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] The present invention relates generally to the field ofcertifications and accreditation (C&A) and, more particularly, to acomputer-implemented system method and medium for certification andaccreditation that assesses the risk of and/or determines thesuitability of a target system to comply with at least one predefinedstandard, regulation and/or requirement.

[0004] 2. Background Description

[0005] The general purpose of C&A is to certify that automatedinformation systems adequately protect information in accordance withdata sensitivity and/or classification levels. In accordance withDepartment of Defense (DoD) Instruction 5200.40, dated Dec. 30, 1997,entitled DoD Information Technology Security Certification andAccreditation Process (DITSCAP), which is incorporated herein byreference in its entirety, certification can be defined as thecomprehensive evaluation of the technical and non-technical features ofan information technology (IT) system and other safeguards, made insupport of the accreditation process, to establish the extent that aparticular design and implementation meets a set of specified securityrequirements. Similarly, as used herein, accreditation can be defined asa formal declaration by a designated approving authority that an ITsystem is approved to operate in a particular security mode using aprescribed set of safeguards at an acceptable level of risk. In generalDISTSCAP is utilized by the DoD for identifying and documenting threatsand vulnerabilities that pose risk to critical information systems.DITSCAP compliance generally means that security risk posture isconsidered acceptable and that potential liability for system “owners”is mitigated.

[0006] The C&A process typically involves a number of policies,regulations, guidelines, best practices, etc. that serve as C&Acriteria. Conventionally, the C&A process is typically a labor intensiveexercise that can require multiple skill sets over a period of timetypically spanning 6-12 months. There can be, for example, severalorganizations and/or individuals that may be involved in the processesof selecting applicable standards, regulations and/or test procedures,and assembling test results and other information into a DITSCAPcompliant package. There is therefore a need to substantially streamlineand expedite the security C&A process in a computer based applicationthat substantially automates the process of performing security riskassessments, certification test procedure development, systemconfiguration guidance, and residual risk acceptance.

SUMMARY OF THE INVENTION

[0007] To address the deficiencies of prior schemes as indicated above,the present invention provides a system, method and medium thatsubstantially automates the security C&A process in a manner thatenhances and facilitates security risk assessments, certification testprocedure development, system configuration guidance, and/or residualrisk acceptance.

[0008] In an exemplary embodiment, the C&A process is automated inaccordance with DoD's DITSCAP requirements. The present invention isnot, however, limited to a DoD environment, and may also be used innon-DoD government as well as civilian/private sector organizationsrequiring risk management and guidance. For example, the system andmethod according to the present invention can also be used to automatethe National Information Assurance Certification and AccreditationProcess (NIACAP).

[0009] An exemplary embodiment according to the present inventioncontemplates a browser based solution that automates the DITSCAPprocess. The browser is preferably directed to five primary elements: 1)gathering information, 2) analyzing requirements, 3) testingrequirements, 4) performing risk assessment, and 5) generatingcertification documentation based on an assessment of the first fourelements.

[0010] The information gathered primarily relates to a description ofthe system to be certified, and its respective components and operatingenvironment (e.g., workstation manufacturer and model, operating systemand version, secret, or top secret operating environment, etc.). Therequirements analysis generally involves selecting by the user a list ofstandards and/or regulations that the system must or should comply with.The user may optionally input his own standards/regulations and/oradditional requirements. Once information is gathered and therequirements analysis is provided, the system intelligently selects aset of test procedures against which the system is tested. Uponcompletion of testing, the risk assessment provides as output anestimate of the risk level for each individual test failed. Each of thefailed tests are also collectively considered and used to evaluate therisk level of the target system as a whole. Then, documentation can beprinted that includes information pertaining to the first four elementsthat would enable an accreditation decision to be made based on theinputs and outputs respectively provided and generated in the first fourelements.

[0011] Before explaining at least one embodiment of the invention indetail, it is to be understood that the invention is not limited in itsapplication to the details of construction and to the arrangements ofthe components set forth in the following description or illustrated inthe drawings. The invention is capable of other embodiments and of beingpracticed and carried out in various ways.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The Detailed Description including the description of a preferredstructure as embodying features of the invention will be best understoodwhen read in reference to the accompanying figures wherein:

[0013]FIG. 1 is an exemplary high level flowchart of a methodcontemplated by at least some embodiments of the present invention;

[0014]FIG. 2 is an exemplary introductory screen shot corresponding tothe flow chart provided in FIG. 1;

[0015]FIG. 3 is an exemplary user login screen shot;

[0016]FIG. 4 is an exemplary project definition screen shot;

[0017]FIG. 5 is an exemplary project definition screen shot showing userselection of either civilian or Department of Defense applicability;

[0018]FIG. 6 is an exemplary project definition screen shot showing userselection of a military branch;

[0019]FIG. 7 is an exemplary project definition screen shot showing userselection of an information category;

[0020]FIG. 8 is an exemplary project definition screen shot showing userselection of a security class;

[0021]FIG. 9 is an exemplary context help screen shot;

[0022]FIG. 10 is an exemplary project hardware screen shot;

[0023]FIG. 11 is an exemplary flow chart of the requirements analysisprocess as contemplated by at least some embodiments of the presentinvention;

[0024]FIG. 12 is an exemplary screen shot used to generate a securityrequirements traceability matrix (SRTM);

[0025]FIG. 13 is an exemplary screen shot showing a display of a SRTM;

[0026]FIG. 14 is an exemplary flow chart illustrating the testingprocess as contemplated by at least some embodiments of the presentinvention;

[0027]FIG. 15 is an exemplary screen shot showing how test planinformation can be edited;

[0028]FIG. 16 is an exemplary screen shot illustrating how a user canselect an existing test procedure and/or create a new test procedure andassociate the test procedure(s) with one or more requirements;

[0029]FIG. 17 is an exemplary screen shot showing how a user can add atest procedure;

[0030]FIG. 18 is an exemplary screen shot showing test procedures thatwill be utilized for C&A;

[0031]FIG. 19 is an exemplary screen shot showing how a user can edit atest procedure;

[0032]FIGS. 20A and 20B are exemplary screen shots that enable a user toenter test results;

[0033]FIG. 21 is an exemplary high level flow diagram of the riskassessment method according to at least some embodiments contemplated bythe present invention;

[0034]FIG. 22 is a table showing three different levels of illustrativethreat categories;

[0035]FIG. 23 is an exemplary screen shot showing a portion of theillustrative threat categories of FIG. 22;

[0036]FIG. 24 is an exemplary scheme by which the risk of an individualtest failure is assessed in accordance with at least some embodimentscontemplated by the present invention;

[0037]FIG. 25 is an exemplary flow diagram of a method of assessingoverall system risk in accordance with at least some embodimentscontemplated by the present invention;

[0038]FIG. 26 is an exemplary flow diagram of the publishing process inaccordance with at least some embodiments contemplated by the presentinvention;

[0039]FIG. 27 is an exemplary screen shot showing how a user can selecta portion of a document for publishing;

[0040]FIG. 28 is an exemplary screen shot that enables a user to editand/or view a portion of a document prior to publishing;

[0041]FIG. 29 is an exemplary screen shot showing how a user can selecta portion of a document for publishing;

[0042]FIG. 30 is an exemplary screen shot illustrating how a user canpublish a portion of a document;

[0043]FIG. 31 illustrates one example of a central processing unit forimplementing a computer process in accordance with a computerimplemented stand-alone embodiment of the present invention;

[0044]FIG. 32 illustrates one example of a block diagram of internalhardware of the central processing unit of FIG. 31;

[0045]FIG. 33 is an illustrative computer-readable medium upon whichcomputer instructions can be embodied, and

[0046]FIG. 34 is an exemplary entity relationship diagram that describesthe attributes of entities and the relationship among them.

DETAILED DESCRIPTION

[0047] Referring now to the drawings, and more particularly to FIG. 1, ahigh level flow diagram is shown that provides an overview of the methodaccording to the present invention. In the first step, information isgathered pertaining to the system or network undergoing C&A. This isindicated by a block 100. The information gathered typically relates toa description of the system to be certified, and its respectivecomponents and operating environment (e.g., workstation manufacturer andmodel, operating system and version, secret, or top secret operatingenvironment, etc.).

[0048] As indicated above, aspects of at least some embodiments of thepresent invention are described in accordance with DoD's DITSCAPrequirements. However, it should be understood that such description isonly by way of example, and that the present invention contemplates usewith regard to any number of types of requirements or environments. Inaddition, within its use with regard to DITSCAP requirements, it shouldbe understood that many of the various aspects and selection options arealso exemplary, as is the fact that information is shown as beingentered via a web browser.

[0049] The requirements analysis generally involves selecting (by ahuman and/or some automated procedure) a list of standards and/orregulations that the system must, or should, comply with. This isindicated by a block 102. Optionally, selection of additionalstandards/regulations and/or requirements by a user is alsocontemplated. At least some embodiments of the present invention thencontemplate automatically displaying/listing each requirement thatcomprises the current security requirements traceability matrix (SRTM),which is derived from the selected set of standards and/or regulationsthat the system must comply with. Additionally, the user will be able tocustomize the current SRTM by either adding, editing and/or deletingrequirements. As known to those skilled in the art, a SRTM can be atable used to trace project lifecycle activities (e.g., testingrequirements) and/or work products to the project requirements. The SRTMcan be used to establish a thread that traces, for example, testingand/or compliance requirements from identification throughimplementation. A SRTM can thus be used to ensure that projectobjectives and/or requirements are satisfied and/or completed.

[0050] Once information is gathered 100 and the requirements analysis102 is provided, the system intelligently selects a set of testprocedures against which the system is tested, as indicated by a block104. The test procedures are selected in a manner so that successfulcompletion of the test procedures will render the system undergoing C&Ato satisfy the SRTM requirements.

[0051] Upon completion of testing 104, the risk assessment step (asindicated by a block 106) then involves assessing for each test failure(should any exist) the vulnerability of the system, as well as the levelof the threat as determined by the information gathered. The riskassessment 106 provides as output an estimate of the risk level for eachindividual test failed. Each of the failed tests are also collectivelyconsidered and used to evaluate the risk level of the system as a whole.Then, documentation can be optionally printed 108 that includesinformation pertaining to the first four elements that would enable anaccreditation decision to be made based on the inputs and outputsrespectively provided and generated in the first four blocks (i.e., 100,102, 104, 106). Each block shown in FIG. 1 (i.e., 100, 102, 104, 106 and108) will be discussed in further detail herein. FIG. 2 is an exemplaryscreen shot corresponding to the blocks (100, 102, 104, 106, 108)provided in FIG. 1. Further information pertaining to the system andmethod according to the present invention can be found in the followingdocument: WEB C&A™, Version 1.0, Sep. 20 2000, available from XactaCorporation, Ashburn, Va. A copy of this document is incorporated hereinby reference in its entirety.

[0052]FIG. 3 shows an exemplary access control screen shot (e.g., foraccess to some or all aspects of the present invention as indicatedabove). Each user can optionally be required to input a valid user nameand password, which provides them with access to only the informationfor which they are responsible. The system can also optionally excludethe password and access feature, providing users access to a set ofpredetermined and/or default information.

Information Gathering

[0053] FIGS. 4-10 show selected exemplary screen shots of theinformation gathering 100 process. Specifically, FIG. 4 shows projectdefinition information, which is assumed to have been selected by tab402. Fields such as project name 430, project version 432, projectacronym 434, project description 436, department 438, and service 440can be provided as being part of the project definition. The projectname 430 field is preferably a read-only field, provided for informationonly. The project version field 432 enables the numeric version of thesystem undergoing C&A to be entered, if applicable. The project acronymfield 434 is optionally used to provide an acronym for the project. Theproject description field 436 can be used to provide a detaileddescription of the project (e.g., mission statement, function, features,and/or capabilities of the system being accredited). The departmentfield 438 can be used to identify the Government (or civilian)department under which this system is being accredited. As shown, thecurrent choice is DoD. The service field 440 is used to identify theService/Agency under which this system is being accredited. As shown,the current choices are Army, Navy, Marine Corps, Air Force, OSD, andOther. Each of the above-identified fields can be tailored to suit aparticular need and/or application.

[0054]FIG. 5 shows how a user can select, via a conventional pulldownmenu, either civilian or DoD service from field 438. FIG. 6 shows how auser can select, via a conventional pulldown menu, a military servicebranch (e.g., Army, Air Force, Marine Corps, OSD, or other) in field 440when DoD is selected in field 438.

[0055] As shown in FIGS. 4-10, tab 404 pertains to the accreditationtype. When a user clicks on the accreditation type tab 404, a menuappears that allows the user to select among one or more top-levelsecurity and accreditation parameters that are used throughout theproject, such as the project name 430, project version 432, projectacronym 434, project description 436, department 438, and service 440fields discussed above.

[0056] When tab 406 is activated, a project security information screen,such as shown in FIG. 7, preferably appears. In a preferred embodiment,FIG. 7 allows a user to input the Information Technology Security(ITSEC) parameters of the system being accredited. Such parameters canpertain to, for example, interfacing mode, processing mode, attributionmode, mission-reliance factor, accessibility factor, accuracy factor,information categories, system class level, and certification analysislevel, as explained in DoD Instruction 5200.40.

[0057] When the user selects information category tab 442, a pull downmenu listing the security levels (e.g., secret, unclassified, sensitive,etc.) appears. FIG. 7 also provides pull down menus for interfacing mode444, attribution mode 446, accessibility factor 448, security class 450,and operating environment 452. The interfacing mode 444, for example,can categorize interaction between systems, and may be through eitherphysical or logical relationships. Exemplary available choices includebenign, passive, and active. The attribution mode 446, for example,distinguishes the degree or complexity of accountability (auditing)required to identify, verify, and trace system entities as well aschanges in their status. The exemplary available choices include none,rudimentary, selected, and comprehensive. The accessibility factor 448relates the degree to and/or relative time at which the operation, data,infrastructure, or system needs to be available from a securityperspective. Exemplary available choices are reasonable, soon, as soonas possible, and immediate. Availability concerns are those that relateto security risks (non-tolerable operational impacts) and does notinclude those that are only performance concerns. The Security Class 450(which can be, e.g., in accordance with the Trusted Computing SecurityEvaluation Criteria (TCSEC), as defined in the DoD Trusted ComputerSystem Evaluation Criteria, DoD 5200.28-STD, dated Dec. 26, 1985,available from Assistant Security Of Defense Command, Control,Communications And Intelligence, Washington, D.C., and which isincorporated herein by reference in its entirety, is used to select theappropriate security requirements from the TCSEC. TCSEC securityrequirements comprise: C1 (Discretionary Security Protection), C2(Controlled Access Protection), B1 (Labeled Security Protection), B2(Structured Protection, B3 (Security Domains), and A1 (VerifiedProtection). The operating environment 452 is utilized to specify thetype of environment where the system is used (e.g., mobile or fixed).

[0058] Also in accordance with DITSCAP requirements, FIG. 8 showspulldown menus for processing mode 454, mission reliance factor 456,accuracy factor 458, common criteria 460, formal access category 462,certification level 464, and total value 466. The processing mode 454distinguishes the way processing, transmission, storage, or data ishandled. Each of the modes exhibits unique security qualities. Theexemplary available choices are dedicated, system high,compartmentalized, and multilevel. The Mission-Reliance Factor 456relates the degree to which the success of the mission relies on theoperation, data, infrastructure, or system. The criticality of themission in a broader context is independent of that factor and can beused separately. The exemplary available choices are preferably none,cursory, partial, and total. The accuracy factor 458 relates the degreeto which the integrity of operation, data, infrastructure, or system isneeded from a security perspective. Integrity concerns are those thatrelate to security risks (non-tolerable operational impacts) and doesnot include those that are only performance concerns. The exemplarychoices are: not applicable, approximate, and exact. Common Criteria 460is the common criteria application profile for the system beingaccredited. For example, the Common Access Protection Profile (CAPP) isselected for most systems operating in the dedicated or systems highmode. The Labeled Security Protection Profile (LSPP) is an exemplarychoice for most compartment-mode or multi-level security systems.

[0059] Formal access category 462 is a designator indicating the levelof formal approval for accessing the system and is related to theclearance levels of users and the maximum data classification processedby the system. Formal access category 462 is in at least someembodiments contemplated by the present invention, to be only applicablefor a system operating in the compartmented mode or multi-level securitymode. There are different definitions for each mode. In a compartmentedmode system, exemplary available options are: 1) No user lacks formalaccess for more than one category being processed; and 2) At least oneuser does not have formal access approval for more than one categorybeing processed. In a Multi-level Security system, the options canbe: 1) All users have formal access approval for all categories of dataprocessed by the system; 2) No user lacks formal access approval formore than one category being processed; and 3) At least one user lacksformal access approval for more than one category being processed.

[0060] Certification Level 464 can be a read-only display of thecalculated Certification Analysis Level. Finally, Total Value 466 can bea read-only display of the total weighted values of the ITSECparameters. These can be used to determine the Certification AnalysisLevel.

[0061] As shown in FIG. 9, by clicking the help tab 468, a contextsensitive help text 470 is provided. The help tab 468 can be invokedwhen, for example, the user is not certain which options to choose inany of the pulldown menus or has a question during any process. Help tab468 can be optionally on any displays where it is believed that contextsensitive help may be needed to assist user understanding.

[0062] When project personnel tab 408 shown in FIG. 4 is activated, amenu (not shown) can be provided that enables a user to enterinformation identifying all the project personnel associated with theaccreditation effort. The personnel are preferably identified by therole, as discussed below, that they serve in the accreditation process.At least one entry for each role is preferably defined for the project.

[0063] For example, the following fields can be provided in a menu (notshown) subsequent to clicking the personnel tab 408:

[0064] Role Name—The role associated with the accreditation team member.The available choices can be:

[0065] Accreditation Team Lead—The person in charge of the accreditationeffort, usually the Project Manager.

[0066] Accreditation Team Member—All the members of the accreditationteam (analysts, testers, etc.).

[0067] Certification Authority (CA)—Person in charge of the systemcertification.

[0068] Certification Authority POC—Point of Contact (POC) to the CA.

[0069] DAA—Designated Approving Authority. Person ultimately responsiblefor the accreditation of the system.

[0070] DAA POC—Point of Contact (POC) to the DAA.

[0071] ISSO—Information System Security Officer. Person responsible forthe security implementation of the system being accredited.

[0072] Organization Responsible—Organization responsible for the designand development of the system being accredited.

[0073] Organization Responsible POC—Point of Contact to the Organizationresponsible.

[0074] Program Manager—Program manager of the system being accredited.

[0075] User Representative—Representative from the user community.

[0076] Title—The title associated with the accreditation team member(Mr., Ms. or Dr., etc.)

[0077] First Name—The first, middle initial, and last name of theaccreditation team member.

[0078] Office—The office (e.g., Office of the Assistant Deputy forPolicy and Planning) of the accreditation team member.

[0079] Office Designation—The office designation of the accreditationteam member. For example, if the office is the Office of the AssistantDeputy for Policy and Planning, then the office designation may beADS-P.

[0080] Organization—An organization that is associated with theaccreditation team member.

[0081] Work Address—A work address if applicable for the accreditationteam member (include city, state and zip code).

[0082] Work Phone—A work phone number for the accreditation team member.

[0083] Work Fax—A work fax number if applicable for the accreditationteam member.

[0084] Email Address—An email address if applicable for theaccreditation team member.

[0085] When the project schedule tab 412 of FIG. 4 is activated, ascreen can appear (not shown) that provides the capability to describeand store each project milestones for the system being accredited.Fields such as milestone title, milestone date, and milestonedescription can be provided.

[0086] When project hardware tab 414 is activated, a menu as shown inFIG. 10 can be provided. The menu allows a user to, for example,Edit/Delete H/W 472, enter various Platform Information 474, CPUinformation 476, and/or Memory/Storage Information 478. This informationcan be modified to reflect changes in system configurations throughoutthe information gathering requirements analysis and testing phases.

[0087] When project operating system 416 is activated, a menu (notshown) that enables a user to describe and store operating systemsassociated with the system hardware is provided. The ability to enterinformation pertaining to multiple operating systems (OS) on eachhardware platform can be provided. Fields are provided to enable a userto enter information pertaining to the OS Name (e.g., Windows NT, AIX,HP UX, etc.), OS Type (e.g., NT, UNIX, etc.), OS Manufacturer (e.g.,Microsoft, Hewlett Packard, IBM, etc.), OS Version (the numeric value ofthe operating system version), OS Options (a list of all OS options (ifany) obtained for this platform), OS Patches (a list of OS patches (ifany) that have been installed on the platform), OS Description (adetailed description of the operating system, possibly including thebasic features, and any functions unique to the system beingaccredited).

[0088] When project application tab 418 is activated, a projectapplication screen appears (not shown) that can provide the analyst withthe ability to describe and store applications associated with thesystem hardware/OS combinations. The following exemplary fields can beprovided: Application Name (the name of the application), ApplicationType (the type of application on the system being accredited—e.g.,database, office automation, e-mail server, etc.), ApplicationManufacturer (the name of the application manufacturer), ApplicationVersion (the numeric version of the application), Application Options (alist of the options associated with the application (if any)),Application Patches (a list of the patches associated with theapplication), and Application Description (a detailed description of theapplication).

[0089] When system interfaces tab 420 is activated, a menu (not shown)is provided that provides the user the ability to describe and store theflow of information into and out of the accredited system. The systeminterfaces entries can describe each of the internal and externalinterfaces identified for the system. The following exemplary fields canbe provided: Interface Name (an internal or external name associatedwith the system interface), and Interface Description (a detaileddescription of the internal or external system interface, whichpreferably includes a statement of the significant features of theinterface as it applies to the entire system, as well as a high leveldiagram of the communications links and encryption techniques connectingthe components of the information system, associated datacommunications, and networks).

[0090] When system data flow tab 422 is activated, a menu (not shown) isprovided that can provide the user the ability to describe and store theflow of information within the accredited system. System data flowentries can describe the flow of information to each of the externalinterfaces identified for the system. The following exemplary fields canbe provided: Data Flow Short Name (a brief user-defined name associatedwith the system data flow), and Data Flow Description (a detaileddescription of the data flow associated with the external interface,which preferably includes a statement of the purpose of the externalinterface and the relationship between the interface and the system, aswell as the type of data and the general method for data transmission,if applicable).

[0091] When accreditation boundary tab 424 is activated, a menu (notshown) that provides the user with the ability to describe and store theidentification of components that are associated with the system beingaccredited, but are outside of the accreditation boundary (i.e., notincluded in the accreditation). This category might include suchequipment/services as, for example, a domain naming service (DNS) usedto translate the host names to IP addresses. The DNS might not be partof the atomic system being accredited, but is required for mostcommunication activities. The following exemplary fields can beprovided: Accreditation Boundary Name (a name associated with theexternal system component), and Accreditation Boundary Description (adetailed description of the external system component, which preferablyincludes the function that this component/service provides the systembeing accredited and its relationship to the system).

[0092] When project threat tab 426 is activated, a menu (not shown)appears that provides the user the ability to quantify the threatenvironment where the system is intended to operate. If the system istargeted to operate in multiple locations, the environmental conditionthat results in the higher or highest level of risk can be selected. Thefollowing exemplary fields can be provided: Location (CONUS (CONtinentalUS) or OCONUS (Outside CONtinenal US) as the primary operating locationfor the system), System Communications (the primary means of informationtransfer to external systems, such as No LAN, Local LAN Only, SIPRNET(SECRET Internet Protocol Router Network), NIPRNET (Unclassified butSensitive Internet Protocol Router Network), Internet, etc.), Connection(the types of connection—e.g., wireless, dial-up, or protecteddistribution system (PDS), etc.), Training Competency Level (e.g.,administrator, maintenance personnel, user, etc.), Installation Facility(the operating environment of the system at its intended end site),Natural Disaster Susceptibility (e.g., fire, flood, lightning, volcano,earthquake, tornado, etc.), and Custom Components.

[0093] When project appendices tab 428 is activated, a menu (not shown)that provides the user the ability to identify external documents thatare associated with the C&A is provided. These appendices can optionallyinclude references to other documents, or consist of the contents ofother documents that are accessible via a computer-implementedembodiment of the present invention. Representative appendices that maybe derived are: System Concept of Operations, Information SecurityPolicy, System Rules of Behavior, Incident Response Plan, ContingencyPlans, Personnel/Technical Security Controls, Memoranda of Agreement,Security, Education, Training and Awareness Plan, and Certification andAccreditation Statement.

[0094] Tabs 402-428 can be activated in any order, and do not need to beactivated sequentially. Also, each tab can be optionally customized tocontain different, fewer, or additional fields relative to the fieldsdiscussed above. Further, the tabs (402-428) can be arrangeddifferently. Fewer or additional tabs can also be provided to suit aparticular application or need.

Requirements Analysis

[0095] The system configuration captured in the step of block 100 ofFIG. 1 is used as input for the determination of the requirementsindicated by block 102. The process of editing and/ordetermining/selecting those requirements is shown in FIG. 11. In atleast some embodiments contemplated by the present invention, theRequirements Analysis step is related to the Accreditation Type 404 andProject Security 406 information stored in the step indicated by block100. In at least some embodiments, data is entered and saved in theAccreditation Type 404 and Project Security 406 fields provided beforebeginning the Requirements Analysis step indicated by block 102.

[0096] In an exemplary embodiment, a general purpose computer on whichthe present invention operates will have stored thereon or have accessto a repository of security regulations and test procedures from variousgovernment and/or civilian departments, agencies, organizations, etc(e.g., such as those from DITSCAP). In step 1102 (FIG. 11), and based atleast in part on the information entered in step 100, pertinentregulations will be selected from this repository, upon which to build asecurity requirement traceability matrix (SRTM) for the C&A. The SRTM,as discussed above, can be a mapping of one or more test procedures toeach individual requirement within a requirements document. Satisfactorycompletion of the respective one or more test procedures that can bemapped to each requirement is generally considered to render therequirement satisfied. However, the user has the flexibility to view andmodify 1104 the SRTM as desired to meet the specific needs of thesystems being accredited by, for example, adding and/or deleting one ormore tests to/from the SRTM, and/or editing one or more of the testprocedures to, for example, include additional testing requirements. Ifthe user decides to modify a test procedure, the specified testprocedure displayed 1106. The user can then modify and save the revisedtest procedure 1108. The user can then either end the editing process orcontinue to modify another security document 1110.

[0097]FIG. 12 shows an exemplary Generate Baseline SRTM screen shot. Inat least some embodiments of the present invention, clicking theRequirements Analysis tab 1201 from the application menu will switchcontrol to the Generate Baseline SRTM screen. As shown, FIG. 12 providesa menu that provides a list of pre-packaged (i.e., shipped with theapplication) regulations documents (1202-1222) for the user to select.Each regulations document (1202-1222) contains specific requirements,one or more of which may be utilized when performing the C&A. Allunmarked check boxes (e.g., check boxes associated with documents 1202,1206, 1210, 1212, 1214, 1216, and 1218) represent unselected RegulationsDocuments, and thus do not factor into the requirements analysis step102 for the particular project under consideration.

[0098] After selections have been made, either by the user by, forexample, clicking the appropriate boxes associated with documents (e.g.,1204, 1208, 1220 and 1224), and/or by the system, the application willprovide a Display SRTM screen as shown in FIG. 13. Additionally, FIG. 13may display any optional user-defined requirements as determined at FIG.12, 1226. FIG. 13 particularly shows pertinent portions of DoD 5200.5,selected in FIG. 12 (1208), that are applicable to the C&A at hand.

Testing

[0099] With the security requirements traceability matrix in place (aportion of which is illustratively shown in FIG. 13), the user proceedsto the testing step 104. In at least some embodiments of the presentinvention, user interfaces will be provided, in accordance with thesteps shown in FIG. 14, for the user to add and/or edit test planinformation 1402, associate all the requirements to test procedures1404, add and/or edit test procedures 1406, enter test results 1408,and/or publish test results 1410. Any of the above steps can optionallybe repeated as needed, as indicated in decision step 1412. Each of thesesteps will be discussed in further detail herein.

[0100] An Edit Test Plan Information screen, corresponding to step 1402,is shown in FIG. 15. The exemplary input fields on the screen areExpected Date of Test 1502, Planned Location of Procedure 1504, TestResources 1506, Test Personnel 1508, and Remarks 1510.

[0101]FIG. 16 is an Associate Requirements screen, corresponding to step1404, which illustrates how a user can select a test procedure toassociate it with at least one requirement selected. (FIG. 18 and theassociated text below will discuss an automated version of this). Asindicated in the descriptive text block 1602, a user can select a sourcerequirements document 1604. Upon clicking on the associate icon 1606, alist of test procedures (not shown) can be displayed. The user can thenselect one or more of the test procedures within the test proceduredatabase (as discussed above) and associate it/them with the selectedsource document 1604. A user can also create a new security test andevaluation procedure (ST&E) 1608 or certification test and evaluation(CT&E) procedure 1610, by clicking on the respective icon. After theuser enters the respective CT&E and/or ST&E information into a formpresented on a new menu (not shown), the user can save the procedure(s)and optionally associate the procedure(s) via the Associate icon, asdescribed above.

[0102]FIG. 17 is a screen illustrating how a user can enter a new testprocedure. As shown, the input fields on the screen are Test Title 1702,Category 1704, I, O, T, D (where I represents interview, O representsobservation, T represents text, and D represents documentation review)1706, Test Procedure 1708, and Expected Result 1710. If Associate 1712is selected, then a new row is preferably created in the test proceduredata base with the data entered in the input fields provided.

[0103]FIG. 18 is a screen showing a display of test procedures that willbe used for a given C&A. The test procedures are intelligently selectedby the present invention for the C&A at hand by using the systeminformation specified in step 100 and the requirements analysis step102. As discussed above in the context of the SRTM, one or more testprocedures within the test procedure database can be mapped to, linkedwith, and/or otherwise associated with each of the individualrequirements within each respective requirements document (FIG. 12). Asshown in FIG. 19, one or more of the test procedures shown in FIG. 18can be edited by, for example, clicking the edit button 1802 in FIG. 18.In a preferred embodiment, the user will be able to edit any of fields1702, 1704, 1706, 1708 and/or 1710.

[0104]FIG. 19 is a screen showing how a user can edit a test procedure.As shown, the user can edit any of the fields Test Title 1702, Category1704, Equipment Under Test 1901, I, O, T, D 1706, Test Procedure 1708and/or Expected Result 1710. Once any of the above fields is edited, theedited results can be saved 1902 or canceled 1904. Context sensitivehelp for any of the above fields is also available 1906.

[0105]FIG. 20A is a screen that enable a user to enter test results. Asshown, at least some embodiment of the present invention contain thefollowing exemplary columns: Category 2002, Test Title 2004, OperatingSystem (OS) 2006, Hardware 2008, Test Procedure 2010 (which enables auser to view the details of the test procedure), Associate Requirements2012 (which allows the user to view which requirements a particular testprocedure is associated with), Enter Results 2014, Complete 2016 (whichprovides an indication of whether the test procedure has beencompleted), and Result 2018 (which provides an indication of whether thetest procedure has passed or failed). (It should be appreciated,however, that various embodiments of the present invention contemplatethat the present invention automatically initiates the test, and obtainsthe results, without the need for any additional manual entry steps).

[0106]FIG. 20B is an exemplary screen that appears when the EnterResults 2014 icon is pressed that is associated with a particular testprocedure. For example, in FIG. 20A, if icon 2014 a is pressed, the ascreen appearing similar in format to FIG. 20B will appear with the TestTitle 1702 corresponding to the test contained in row 2002 a of FIG. 20A(e.g., Cannot Log On Directly as Root from Remote System/Terminal). Asshown, the Test Title 1702, Category 1704, Equipment Under Test 1901, I,O, T, D 1706, Test Procedure 1708 and/or Expected Result 1710 and fieldsalso preferably appear within this screen. Also, Result field 2020appears, which allows the user to enter the test result (e.g., pass orfail). Tester field 2022 enables the tester to provide his name, andDate 2024 that the test was conducted. Finally, the tester is able toenter any Notes pertaining to the test 2026.

Risk Assessment

[0107] Once the testing step 104 has been completed and the resultsrecorded, the risk assessment step 106 commences, as indicated bysub-headings a-d below.

a) Generate Project Threat Profile (Step 2102)

[0108] As shown in FIG. 21, at step 2102, at least some embodiments ofthe present invention generate a project threat profile, which is ascore for each of the generic threat elements (e.g., fire, flood,hardware, power, software design error, etc.) as will be discussed infurther detail herein. In at least some embodiments, the user performingthe C&A is presented with a series of questions pertaining to theenvironment for which the C&A will be performed. (This information couldalso be obtained in an automated fashion using any number of knowntechniques). The present invention will then estimate the threat levelbased on the operators' answer. The value assigned to each of thegeneric threat elements is applicable to each test procedure associatedwith the particular system undergoing C&A. A user can optionally changeany of the system determined threat element scores for one or more ofthe generic threat elements. Exemplary values for generic threatelements are as follows: Threat Element Score Interpretation N Threatelement is not applicable to this project or has negligible likelihoodof occurrence L Threat element has low likelihood of occurrence for thisproject M Threat element has medium likelihood of occurrence for thisproject H Threat element has high likelihood of occurrence for thisproject

[0109] For example, generic threat elements 1-29, as defined in FIG. 22,may have a project threat profile as follows:

[0110] MHNLLLLMMMMMLLLMMMMLLLLLLLLNN

[0111] corresponding, respectively, to elements 1-29. For this projectthreat profile, the threat of a flood is thus considered high.

[0112]FIG. 23 shows an exemplary Threat Environment screen, which showsthe calculated level of risk based on the information that was providedin step 100. As per at least some embodiments, the present inventionautomatically calculates the risk, which is indicated under theCalculated Value 2302 heading. This could be accomplished in any numberof ways based upon data obtained during the current and/or testingphase, as indicated above. The User Defined Value 2234 preferablydefaults to the corresponding Calculated Value 2302 for a given threatenvironment element (e.g., 1, 2, 3, etc.). However the user/analyst hasthe opportunity to optionally override the calculated risk rating byclicking on the User Defined Value 2204 for each corresponding threatelement. As previously discussed, exemplary available choices arenegligible, low, medium, or high, although they could also be, e.g.,numerical in nature.

b) Threat Correlation String (Step 2104)

[0113] In step 2104, a threat correlation for each failed test procedureis accessed. Specifically, each test procedure used in the C&A for thesystem being evaluated is, in at least some embodiments of the presentinvention, coded with a threat correlation string, with each characterin the string representing one of the generic threat elements in thesame order as they exist in the project threat profile as shown, forexample, in FIG. 22. The test procedure database preferably containsthese codes. Each character in the threat correlation string contains ascore that indicates the relative potential of a given threat to exploita vulnerability caused by failure of this particular test. An exemplaryscoring system is as follows: Threat Correlation Score Interpretation NThreat element is not applicable to this vulnerability (or hasnegligible potential to exploit it) L Threat element has low potentialfor exploit of this vulnerability M Threat element has medium exploitpotential for this vulnerability H Threat element has high exploitpotential for this vulnerability

[0114] Thus, for example, failure of a particular test may mean that thesystem being tested is highly vulnerable to Floods. To indicate this,the character in the threat correlation string corresponding to Floodswould contain a score of “H”.

c) Determine Risk Profile for Each Failed Test Procedure (Step 2106)

[0115] As indicated at step 2106, the risk profile for each testprocedure is determined. Specifically, for each test failure, the threatcorrelation string contained within each test procedure, as determinedat step 2104, is applied against the project threat profile asdetermined at step 2102.

[0116] For example, the project threat profile above, given as:

[0117] MHNLLLLMMMMMLLLMMMMLLLLLLLLNN

[0118] may have a test procedure with the following threat correlationsting:

[0119] HHNMHLMNHHHMLNNNHLMLHNNLHHLMH

[0120] In this case, in accordance with an exemplary process accordingto at least some embodiments of the present invention, the combined riskprofile string as determined in accordance with FIG. 24 would be:

[0121] MHNLMLLNMMMMLLLNMLMLMLLMMLNN

[0122] For a given row of FIG. 24, and given the first two valuescontained in the first two columns corresponding to that row, we havediscovered and determined that the values contained in the third columnof the row can be used a measure or risk.

[0123] The highest risk level in the combined string for a given testprocedure is preferably used as the risk level for the failure of thattest procedure. Thus, for the combined string above, the risk level fora failure of the test procedure is high, since there is an H in thesecond position. Similarly, if M were the highest risk level thatappears in a combined string, then the risk level for a failure of thattest procedure would be medium, etc.

d) Determine Overall System Level Risk (Step 2108)

[0124] In addition to the individual risk level scores for each testfailure as determined in step 2106, an overall risk level for theproject is also determined as indicated by step 2108. As shown in FIG.25, in at least some embodiments, of the present invention, the overallsystem risk level is defined as the highest of the individual riskelements. Thus, if it is determined that any element in the risk profileassociated with the failure of any given test procedure is “high” (asindicated by decision block 2502), then the overall risk for the systemis high as indicated by a block 2504. If the risk profile associatedwith the failure of any given test procedure is “medium” (as indicatedby decision block 2506), then the overall risk for the system is mediumas indicated by a block 2508 when no high risk test failures arepresent. If the risk profile associated with the failure of any giventest procedure is “low” (as indicated by decision block 2510), then theoverall risk for the system is low when no high risk or medium riskfailures are present, as indicated by a block 2512. If the risk profileassociated with the failure of any given test procedure is “negligible”then the overall risk for the system is negligible, as indicated by ablock 2514, when no high risk, medium risk, or low risk failures arepresent. The user also can have the ability to override the overallsystem risk level as determined in accordance with the abovemethodology. In such a case, the user will also be able to optionallyprovide explanatory text to accompany the overall user-defined systemrisk level.

Publishing

[0125] In the publishing step 108, the present invention collates theresults of the certification process and optionally generates thedocuments needed for accreditation. The present invention takes theinformation gathered during the steps corresponding to blocks 100, 102,104 and 106, and reformats the information by, for example, organizingit into to appropriate documents, document subsections or subparagraphs,sections and/or appendices, etc.

[0126] As shown in FIG. 26, the invention allows a user to select adocument or subsection thereof for publishing 2602, and to optionallyinput and/or review the information thereof 2604. As shown in FIG. 27,to view the document subsection thereof, the user simply clicks on thesection name 2702. As shown in FIG. 28, the user can then edit theselection subsection 2702. The user can optionally edit, inputinformation, or review the existing text 2604 or add to it, or evenupload graphics if desired to further customize the final document. Ifthe user chooses to publish the document or subsection underconsideration 2606, the publishing function 2808, as shown in FIG. 29,can also, as previously discussed, generate any Appendices desired bythe user and/or required by, for example, the DITSCAP (DoD Instruction5200.40). At decision step 2810, the process can either be repeated foranother document or subsection, or terminated. FIG. 30 shows anexemplary screen shot that enables a user to publish 2902 the acronymlist 2902 selected in FIG. 29. The present invention also contemplatesthat accreditation can be automated, so that no accreditation agency isneeded. In this embodiment, when sufficient test related results and/orinformation is provided to the computer 3102, the method according tothe present invention can automatically determine that accreditationrequirements have been satisfied.

Computer Implementation

[0127] The techniques of the present invention may be implemented on acomputing unit such as that depicted in FIG. 31. In this regard, FIG. 31is an illustration of a computer system which is also capable ofimplementing some or all of the computer processing in accordance withcomputer implemented embodiments of the present invention. Theprocedures described herein are presented in terms of program proceduresexecuted on, for example, a computer or network of computers.

[0128] Viewed externally in FIG. 31, a computer system designated byreference numeral 3100 has a computer portion 3102 having disk drives3104 and 3106. Disk drive indications 3104 and 3106 are merely symbolicof a number of disk drives which might be accommodated by the computersystem. Typically, these could include a floppy disk drive 3104, a harddisk drive (not shown externally) and a CD ROM indicated by slot 3106.The number and type of drives vary, typically with different computerconfigurations. Disk drives 3104 and 3106 are in fact optional, and forspace considerations, are easily omitted from the computer system usedin conjunction with the production process/apparatus described herein.

[0129] The computer system 3100 also has an optional display 3108 uponwhich information, such as the screens illustrated in, for example,FIGS. 4-10, etc. may be displayed. In some situations, a keyboard 3110and a mouse 3112 are provided as input devices through which input maybe provided, thus allowing input to interface with the centralprocessing unit 3102. Then again, for enhanced portability, the keyboard3110 is either a limited function keyboard or omitted in its entirety.In addition, mouse 3112 optionally is a touch pad control device, or atrack ball device, or even omitted in its entirety as well, andsimilarly may be used as an input device. In addition, the computersystem 3100 may also optionally include at least one infrared (or radio)transmitter and/or infrared (or radio) receiver for either transmittingand/or receiving infrared signals.

[0130] Although computer system 3100 is illustrated having a singleprocessor, a single hard disk drive and a single local memory, thesystem 3100 is optionally suitably equipped with any multitude orcombination of processors or storage devices. Computer system 3100 is,in point of fact, able to be replaced by, or combined with, any suitableprocessing system operative in accordance with the principles of thepresent invention, including hand-held, laptop/notebook, mini, mainframeand super computers, as well as processing system network combinationsof the same.

[0131]FIG. 32 illustrates a block diagram of the internal hardware ofthe computer system 3100 of FIG. 31. A bus 3202 serves as the maininformation highway interconnecting the other components of the computersystem 3100. CPU 3204 is the central processing unit of the system,performing calculations and logic operations required to execute aprogram. Read only memory (ROM) 3206 and random access memory (RAM) 3208constitute the main memory of the computer 3102. Disk controller 3210interfaces one or more disk drives to the system bus 3202. These diskdrives are, for example, floppy disk drives such as 3104 or 3106, or CDROM or DVD (digital video disks) drive such as 3212, or internal orexternal hard drives 3214. As indicated previously, these various diskdrives and disk controllers are optional devices.

[0132] A display interface 3218 interfaces display 3208 and permitsinformation from the bus 3202 to be displayed on the display 3108. Againas indicated, display 3108 is also an optional accessory. For example,display 3108 could be substituted or omitted. Communications withexternal devices, for example, the other components of the systemdescribed herein, occur utilizing communication port 3216. For example,optical fibers and/or electrical cables and/or conductors and/or opticalcommunication (e.g., infrared, and the like) and/or wirelesscommunication (e.g., radio frequency (RF), and the like) can be used asthe transport medium between the external devices and communication port3216. Peripheral interface 3220 interfaces the keyboard 3110 and themouse 3112, permitting input data to be transmitted to the bus 3202.

[0133] In alternate embodiments, the above-identified CPU 3204, may bereplaced by or combined with any other suitable processing circuits,including programmable logic devices, such as PALs (programmable arraylogic) and PLAs (programmable logic arrays). DSPs (digital signalprocessors), FPGAs (field programmable gate arrays), ASICs (applicationspecific integrated circuits), VLSIs (very large scale integratedcircuits) or the like.

[0134] One of the implementations of the invention is as sets ofinstructions resident in the random access memory 3208 of one or morecomputer systems 3100 configured generally as described above. Untilrequired by the computer system, the set of instructions may be storedin another computer readable memory, for example, in the hard disk drive3214, or in a removable memory such as an optical disk for eventual usein the CD-ROM 3212 or in a floppy disk (e.g., floppy disk 3302 of FIG.33) for eventual use in a floppy disk drive 3104, 3106. Further, the setof instructions (such as those written in the Java programming language)can be stored in the memory of another computer and transmitted via atransmission medium such as a local area network or a wide area networksuch as the Internet when desired by the user. One skilled in the artknows that storage or transmission of the computer program mediumchanges the medium electrically, magnetically, or chemically so that themedium carries computer readable information.

[0135]FIG. 34 is an entity relationship diagram (ERD) that describes theattributes of entities and the relationships among them, and illustratesthe basic data abstraction of an embodiment of the system. As known tothose skilled in the art, an ERD is a conceptual representation of realworld objects and the relationships between them. It defines informationthat the systems create, maintain, process, and delete, as well as theinherent relationships that are supported by the database (i.e., datastore).

[0136] At least some embodiments of the present invention can utilize arelational database to store and organize all information such as, forexample, test procedures, standards/regulations, and user enteredinformation. The design of an embodiment of the database is provided inthe ERD shown in FIG. 34. The database is initially populated withsecurity requirements, test procedures and related information tofacilitate the operation of the system. As information is entered by theuser and calculated by the system, it is also recorded in the database.At least some embodiments of the present invention produce outputdocumentation that can be formatted in accordance with, for example,DlTSCAP and/or NIACAP standard(s).

[0137] The ERD shown in FIG. 34 uses conventional notation. Each entity,as shown in FIG. 34, comprises a rectangular box. A one-to-one (1:1)relationship indicates that each occurrence of entity A is related toonly one of entity B and each occurrence of B is related to only oneoccurrence of A. A 1:1 relationship is indicated by a single lineconnecting two entities.

[0138] A one-to-many (1:M) relationship indicates that each occurrenceof entity A is related to one or more occurrences of entity B, but eachoccurrence of entity B is related to only one occurrence of entity A.The two vertical lines shown below indicate that entity A is associatedonly with entity B. If the two vertical lines are not present, entity Acan be associated with two or more entities (e.g., B, C and/or D).

[0139] A many-to-many (N:M) relationship shows that each occurrence ofentity A is related to one or more occurrences of entity B, and eachoccurrence of entity B is related to one or more occurrences of entityA.

[0140] If there can be occurrences of one entity that are not related toat least one occurrence of the other entity, then the relationship isoptional and this is shown by the use of a dashed line.

[0141] As known to those skilled in the art, a data dictionary, asprovided below, defines and specifies the data elements in the system.The data dictionary shown below can be used either as a stand-alonesystem or as an integral part of the database. Data integrity andaccuracy is better ensured in the latter case.

[0142] An instance of an entity shown in FIG. 34 will represent one ormore lines associated with the Table column in the data dictionaryprovided below (i.e., an entity shown in FIG. 34 can have many dataitems/attributes). These data items, representing an attribute of eachrespective entity to which it belongs, are shown in each line of thedata dictionary. The data dictionary also provides the DataType (e.g.,varchar, bit, decimal, char, text, int, etc.), and Length (incharacters) of the field. The Precision column is applicable only tonumerical data and represents the maximum number of significant digits.The Null column indicates whether the field defaults to a null value.FIG. 34 and the data dictionary can be used to produce, for example, theSQL code required to create the data structures in the database.

[0143] The table below provides an exemplary data dictionary that can beused with the ERD of FIG. 34. Database Table Column DataType LengthPrecision Null AccessCategory FormalAccess int 4 10 NO FormalAccessTextvarchar 50 0 YES Rank int 4 10 YES AccessibilityFactorAccessibilityFactor varchar 50 0 NO Rank int 4 10 YESAccreditationBoundary PID decimal 9 18 NO Name varchar 50 0 YESDescription text 16 0 YES ADID int 4 10 YES AccreditationLookupAccreditationCategor varchar 50 0 NO y AccreditationType varchar 50 0 NOAccreditationProfileQuestio ID int 4 10 NO Message text 16 0 YESAccreditationTypeMessage Id int 4 10 NO Choice varchar 50 0 YES Messagevarchar 255 0 YES AccuracyFactor AccuracyFactor varchar 50 0 NO Rank int4 10 YES AISCertLevelLookup CertLevel varchar 50 0 NO Analysts AID int 410 NO username varchar 25 0 NO Fname varchar 20 0 NO Lname varchar 20 0NO Telephone varchar 20 0 YES Email varchar 50 0 YES

[0144] Database Table Column DataType Length Precision Null Classvarchar 10 0 NO State varchar 10 0 NO Application AppID int 4 10 NOApplicationName varchar 50 0 YES ApplicationManufactu varchar 50 0 YESrer ApplicationType varchar 50 0 YES OSID int 4 10 NOApplicationDescripti ntext 16 0 YES on ApplicationVersion varchar 50 0YES ApplicationOptions varchar 255 0 YES ApplicationPatches varchar 2550 YES ApplicationName ApplicationName varchar 50 0 NOApplicationManufactu varchar 50 0 NO rer ApplicationType ApplicationTypevarchar 50 0 YES Type char 1 0 YES AttributionMode AttributionModevarchar 50 0 NO Rank int 4 10 YES AuditData AuditDataID int 4 10 NO PIDdecimal 9 18 YES ProjectName varchar 50 0 YES SectionName char 6 0 NOAspPageName varchar 50 0 NO Action char 1 0 NO TableName varchar 50 0YES Status char 7 0 NO ErrorMessage text 16 0 YES ErrorNumber int 4 10YES UserName varchar 25 0 NO DateTimeStamp datetime 8 23 NO CCClassClass varchar 50 0 YES

[0145] Database Table Column DataType Length Precision NullClassification ID int 4 10 NO ClearanceLevel varchar 50 0 YESClassificationLevelWeight ID int 4 10 NO Characteristic varchar 255 0YES Alternative varchar 255 0 YES Weight float 8 53 YES CRClist FileNamevarchar 250 0 NO CheckSum varchar 50 0 NO Date varchar 50 0 YES Versionfloat 8 53 NO DataFlow DFID int 4 10 NO DataFlowDescription text 16 0YES PID decimal 9 18 NO ShortName varchar 50 0 YES DBFigure ID int 4 10NO PID decimal 9 18 NO FigureName varchar 255 0 NO FigureNumber int 4 10YES FigureType varchar 50 0 YES Document varchar 50 0 YES Content image16 0 YES FigureTitle varchar 255 0 YES Paragraph varchar 50 0 YESDepartment Department varchar 50 0 NO Type char 1 0 YES DocumentStatusPID decimal 9 18 NO SSAA bit 1 1 NO AppenA bit 1 1 NO

[0146] Database Table Column DataType Length Precision Null AppenB bit 11 NO AppenC bit 1 1 NO AppenD bit 1 1 NO AppenE bit 1 1 NO AppenF bit 11 NO AppenG bit 1 1 NO AppenH bit 1 1 NO AppenI bit 1 1 NO AppenJ bit 11 NO AppenK bit 1 1 NO AppenL bit 1 1 NO AppenM bit 1 1 NO AppenN bit 11 NO AppenO bit 1 1 NO AppenP bit 1 1 NO AppenQ bit 1 1 NO AppenR bit 11 NO FacilityLookup Rank int 4 10 YES FacilityType varchar 50 0 YESHardware EUTID int 4 10 NO PID decimal 9 18 NO PlatformName varchar 50 0YES PlatformDescription ntext 16 0 YES PlatformType varchar 50 0 YESPlatformDisplay varchar 50 0 YES RAM varchar 50 0 YESPlatformManufacturer varchar 50 0 YES PlatformModel varchar 50 0 YESCPUName varchar 50 0 YES CPUQuantity varchar 50 0 YES CPUSpeed varchar50 0 YES DiskSpace varchar 255 0 YES DiskDescription text 16 0 YESHardwareOptions varchar 255 0 YES

[0147] Database Table Column DataType Length Precision NullPlatformQuantity int 4 10 YES OtherStorage varchar 255 0 YESInformationCategory InformationCatagory varchar 50 0 NO Rank int 4 10YES InformationStatus PID decimal 9 18 NO ProjectDef char 1 0 NOAccredType char 1 0 NO ProjectSec char 1 0 NO SecReqDoc char 1 0 NOProjectPersonnel char 1 0 NO SystemUsers char 1 0 NO ProjectHardwarechar 1 0 NO ProjectOS char 1 0 NO ProjectApps char 1 0 NOProjectSchedule char 1 0 NO ProjectDataFlow char 1 0 NOProjectInterfaces char 1 0 NO AccredBoundary char 1 0 NO ProjectThreatchar 1 0 NO AppendixD char 1 0 NO AppendixE char 1 0 NO AppendixH char 10 NO AppendixI char 1 0 NO AppendixJ char 1 0 NO AppendixK char 1 0 NOAppendixL char 1 0 NO AppendixM char 1 0 NO AppendixN char 1 0 NOAppendixO char 1 0 NO AppendixP char 1 0 NO AppendixR char 1 0 NOProjectHardwareMod char 1 0 NO ProjectOSMod char 1 0 NOProjectCertLevelMod char 1 0 NO

[0148] Database Table Column DataType Length Precision Null InterfacesIID int 4 10 NO InterfaceName varchar 50 0 YES InterfaceAcronym varchar50 0 YES InterfaceDescription text 16 0 YES PID decimal 9 18 NOInterfacingMode InterfaceMode varchar 50 0 NO Rank int 4 10 YESLevelDetermination ID int 4 10 YES WeightedTotalMin float 8 53 YESWeightedTotalMax float 8 53 YES Class int 4 10 YES Description varchar255 0 YES MasterAcronym Acronym varchar 50 0 YES Description text 16 0YES Service varchar 50 0 YES MasterChecklistSource SectionName varchar255 0 NO Question varchar 50 0 NO Text text 16 0 YES QuestionSort int 410 YES MasterDefinition Term varchar 50 0 YES Definition text 16 0 YESMinClearanceLookup Clearance varchar 50 0 NO Rank int 4 10 YES MRFactorMissionRelianceFacto varchar 50 0 NO r Rank int 4 10 YESMultilevelSecurityClass ID int 4 10 YES

[0149] Database Table Column DataType Length Precision Null MaxDataClassvarchar 255 0 YES MinUserClear varchar 255 0 YES Case1 varchar 255 0 YESCase2 varchar 255 0 YES Case3 varchar 255 0 YES NetworkLookup Rank int 410 YES Network varchar 50 0 YES OperatingSystem OSID int 4 10 NO OSNamevarchar 50 0 YES OSType varchar 50 0 NO OSVersion varchar 50 0 YESOSManufacturer varchar 50 0 YES OSDescription text 16 0 YES OSOptionsvarchar 255 0 YES OSPatches varchar 255 0 YES Fixes varchar 50 0 YESServicePack varchar 50 0 YES EUTID int 4 10 NO OrganizationAnalyst OrgIDint 4 10 NO AID int 4 10 NO Organizations OrgID int 4 10 NOOrganizationName varchar 50 0 NO OrganizationDescript varchar 500 0 YESion OSName OSName varchar 50 0 NO OSManufacturer varchar 50 0 NO Typechar 1 0 YES OSTypeLookup Rank int 4 10 NO OSType varchar 50 0 NOPlatformName

[0150] Database Table Column DataType Length Precision NullPlatformManufacturer varchar 50 0 NO Type char 1 0 YES PlatformTypePlatformType varchar 50 0 YES Type char 1 0 YES ProcedureTemplate ID int4 10 YES Cat1 varchar 50 0 YES Cat2 varchar 50 0 YES Cat3 varchar 50 0YES Platform varchar 50 0 YES Text text 16 0 YES ExpectedResult text 160 YES Instance varchar 50 0 YES TestTitle varchar 100 0 YES TestNumbervarchar 50 0 NO CertAnalysisLevel int 4 10 YES Threat varchar 50 0 YESImpactStatement text 16 0 YES I char 1 0 YES O char 1 0 YES T char 1 0YES D char 1 0 YES TemplateID int 4 10 NO ProcessingMode ProcessModevarchar 50 0 NO Rank int 4 10 YES Project PID decimal 9 18 NOProjectName varchar 50 0 NO ProjectDescription text 16 0 YESProjectClassificatio varchar 50 0 NO n InterfaceMode varchar 50 0 YESInformationCategory varchar 50 0 YES AccreditationType varchar 50 0 YESProcessingMode varchar 50 0 YES

[0151] Database Data Table Column Type Length Precision NullAttributionMode varchar 50 0 YES MRFactor varchar 50 0 YESAccessibilityFactor varchar 50 0 YES AccuracyFactor varchar 50 0 YESOrgID int 4 10 NO SecurityMode varchar 50 0 YES ProjectAcronym varchar50 0 YES MinClearance varchar 50 0 YES FormalAccess varchar 50 0 YESProjectVersion varchar 50 0 YES Environment varchar 50 0 YESSecurityClass varchar 50 0 YES MaxLevel varchar 50 0 YESAccreditationSubType varchar 50 0 YES IMVal int 4 10 YES PMVal int 4 10YES AMVal int 4 10 YES MRFVal int 4 10 YES AF1Val int 4 10 YES AF2Valint 4 10 YES ICVal int 4 10 YES TotalVal int 4 10 YES CertLevel int 4 10YES ThreatString varchar 50 0 YES InformationSubCatego varchar 50 0 YESry CCClass varchar 50 0 YES Department varchar 50 0 YES Service varchar50 0 YES SecRegChange varchar 50 0 YES SRTMChange varchar 50 0 YESProjectCalcRisk varchar 50 0 YES ProjectUserRisk varchar 50 0 YESProjectRiskDescripti text 16 0 YES on Status varchar 50 0 YESSubscriptionKey varchar 50 0 NO OpSysFolder varchar 50 0 YES Criteriavarchar 50 0 YES

[0152] Database Table Column DataType Length Precision NullProjectAcronym ID int 4 10 NO PID decimal 9 18 NO Acronym varchar 50 0YES Description text 16 0 YES ProjectAppendixFile PID decimal 9 18 NOAppendix varchar 50 0 NO Instance int 4 10 NO PrintOrder int 4 10 YESTitle varchar 255 0 YES ShortTitle varchar 50 0 YES Author varchar 50 0YES Date varchar 50 0 YES Version varchar 50 0 YES Url varchar 255 0 YESStatus char 1 0 YES AppendixCFlag char 1 0 YES FileImage image 16 0 YESFileName varchar 50 0 YES FileType varchar 50 0 YESProjectAppendixGHLeadinD PID decimal 9 18 NO Appendix varchar 50 0 YESExpectedDate text 16 0 YES PlannedLocation text 16 0 YES TestPersonneltext 16 0 YES TestResources text 16 0 YES TestPlanRemarks text 16 0 YESProjectChecklistResult PID decimal 9 18 NO SectionName varchar 255 0 YESQuestion varchar 50 0 YES Result varchar 50 0 YESProjectClassificationLookup Rank int 4 10 NO

[0153] Database Table Column DataType Length Precision NullProjectClassification varchar 50 0 YES ProjectDefinition ID int 4 10 NOPID decimal 9 18 NO Term varchar 255 0 YES Definition text 16 0 YESProjectOtherDocument DocID int 4 10 NO PID decimal 9 18 NO Title varchar255 0 YES ShortTitle varchar 50 0 YES Author varchar 50 0 YES Versionvarchar 50 0 YES Date varchar 50 0 YES Url varchar 255 0 YESProjectPersonnel RoleID int 4 10 NO RoleName varchar 50 0 YES Titlevarchar 50 0 YES FName varchar 50 0 YES MI varchar 50 0 YES LNamevarchar 50 0 YES Office varchar 50 0 YES Organization varchar 50 0 YESAddress1 varchar 50 0 YES Address2 varchar 50 0 YES City varchar 50 0YES State varchar 50 0 YES Zip varchar 50 0 YES Phone varchar 50 0 YESOfficeDesignation varchar 50 0 YES PID decimal 9 18 NO Fax varchar 50 0YES Email varchar 50 0 YES ProjectReference RefID int 4 10 NO

[0154] Database Table Column DataType Length Precision Null PID decimal9 18 NO Title varchar 255 0 YES ShortTitle varchar 255 0 YES Authorvarchar 50 0 YES Date varchar 50 0 YES Version varchar 50 0 YES Urlvarchar 255 0 YES Type char 1 0 YES SpecID int 4 10 YES Appendix varchar50 0 YES Instance int 4 10 YES ProjectReq PRID int 4 10 NO PID decimal 918 NO SPECID int 4 10 YES SourceDoc varchar 50 0 NO ReqID int 4 10 YESParagraph varchar 255 0 NO Title varchar 255 0 NO Category1 varchar 2550 YES Category2 varchar 255 0 YES Stated varchar 2000 0 NO RequirementInterview varchar 255 0 YES Demonstration varchar 255 0 YES Test varchar255 0 YES Observation varchar 255 0 YES Result varchar 255 0 YESCertReport varchar 255 0 YES Reference Requirement varchar 255 0 YESType Reference varchar 255 0 YES Requirement Doc Reference varchar 255 0YES Requirement Par Cat1 char 255 0 YES Cat2 char 255 0 YES Cat3 char255 0 YES TestNumber varchar 50 0 YES AlreadyPulled varchar 255 0 YESTemplateID int 4 10 YES

[0155] Database Table Column DataType Length Precision Null Type char 10 NO ProjectRiskElement PID decimal 9 18 NO TestId int 4 10 NOTestFailure varchar 100 0 NO AssociatedRequirement text 16 0 YESStatementofIssue text 16 0 YES ImpactStatement text 16 0 YES Safeguardtext 16 0 YES RiskAssessment text 16 0 YES CalcRiskLevel varchar 50 0YES UserRiskLevel varchar 50 0 YES ThreatCorrelation varchar 50 0 YESProjectSpec PID decimal 9 18 NO specid int 4 10 NOProjectSystemThreatEnviron PID decimal 9 18 YES ThreatElement varchar 500 YES CalcValue varchar 50 0 YES UserDefinedValue varchar 50 0 YESThreatCategory varchar 50 0 YES ProjectTestProcedure PID decimal 9 18 NOTestID int 4 10 NO Cat1 varchar 50 0 YES Cat2 varchar 50 0 YES Cat3varchar 50 0 YES Text text 16 0 YES ExpectedResult text 16 0 YES Resultvarchar 50 0 YES Notes text 16 0 YES Tester varchar 50 0 YES Datedatetime 8 23 YES HWPlatform varchar 50 0 YES TestNumber varchar 50 0YES

[0156] Database Table Column DataType Length Precision NullTestNumberType varchar 50 0 YES Threat varchar 50 0 YES ImpactStatementtext 16 0 YES TestTitle varchar 100 0 YES I char 1 0 YES O char 1 0 YEST char 1 0 YES D char 1 0 YES EUTID int 4 10 YES AssociatedRequirementtext 16 0 YES TemplateID int 4 10 YES Type char 1 0 NO OSType varchar 500 YES ProjectThreatEnvironment PID decimal 9 18 NO Location varchar 50 0YES Network varchar 50 0 YES Wireless varchar 50 0 YES Dialup varchar 500 YES PDS varchar 50 0 YES AdminTraining varchar 50 0 YES MaintTrainingvarchar 50 0 YES UserTraining varchar 50 0 YES InstallationFacilityvarchar 50 0 YES Flood varchar 50 0 YES Fire varchar 50 0 YES Lightningvarchar 50 0 YES Tornado varchar 50 0 YES Volcano varchar 50 0 YESEarthquake varchar 50 0 YES CustomHardware varchar 50 0 YESCustomSoftware varchar 50 0 YES ProjectThreatEnvCalc varchar 50 0 YESProjectThreatEnvUser varchar 50 0 YES RequirementCat1Lookup Rank int 410 YES

[0157] Database Table Column DataType Length Precision Null Categoryvarchar 50 0 YES Type varchar 50 0 YES RequirementStatus SRTMGeneratedbit 1 1 NO PID decimal 9 18 NO ReqCustomized bit 1 1 NO UDRAdded bit 1 1NO BaselineMod bit 1 1 NO RiskStatus PID decimal 9 18 NO Failurespulledchar 1 0 NO RiskAnalyzed char 1 0 NO ThreatOverride char 1 0 NORoleLookup RoleName varchar 50 0 YES SecurityClass ID int 4 10 NO Clsvarchar 50 0 YES SecurityRegSelection Department varchar 50 0 NO Servicevarchar 50 0 NO SpecId int 4 10 NO SecurityRegulationCriteria PIDdecimal 9 18 NO F1 char 10 0 YES F2 char 10 0 YES F3 char 10 0 YES F4char 10 0 YES F5 char 10 0 YES F6 char 10 0 YES F7 char 10 0 YES F8 char10 0 YES F9 char 10 0 YES F10 char 10 0 YES F11 char 10 0 YES F12 char10 0 YES

[0158] Database Table Column DataType Length Precision NullSecurityRegulationCriteriaQ SecurityRegulation int 4 10 YESCriteriaQuestID Code varchar 255 0 YES Message varchar 255 0 YESSecurityRegulations SpecID int 4 10 NO SecurityRegulations varchar 255 0YES Title varchar 255 0 YES SourceDoc varchar 50 0 YES Service varchar50 0 YES Department varchar 50 0 YES Qualifier varchar 50 0 YES Authorvarchar 50 0 YES Date varchar 50 0 YES Version varchar 50 0 YES Urlvarchar 255 0 YES Type char 1 0 YES Service Service varchar 50 0 NODepartment varchar 50 0 NO Type char 1 0 YES SRTMSource ID int 4 10 NOSPECID int 4 10 NO SourceDoc varchar 255 0 NO Paragraph varchar 255 0YES Title varchar 255 0 YES Category varchar 255 0 YES StatedRequirementvarchar 2000 0 NO Class varchar 255 0 YES SubCategory varchar 255 0 YESI varchar 255 0 YES D varchar 255 0 YES T varchar 255 0 YES O varchar255 0 YES AccreditationType varchar 255 0 YES

[0159] Database Table Column DataType Length Precision Null Criteriavarchar 255 0 YES Requirement varchar 255 0 YES Type Reference varchar255 0 YES Requirement Doc Reference varchar 255 0 YES Requirement ParMethod varchar 255 0 YES Cat1 varchar 255 0 YES Cat2 varchar 255 0 YESCat3 varchar 255 0 YES TestNumber varchar 50 0 YES SsaaPara PID decimal9 18 NO ParaNumber varchar 255 0 NO Para text 16 0 YES Description IDint 4 10 NO Document varchar 50 0 NO SSAAParaTitle ID int 4 10 NO Titlevarchar 60 0 NO Paragraph varchar 50 0 NO Document varchar 50 0 NOService varchar 50 0 YES Command varchar 50 0 YES SSAAStatus PID decimal9 18 NO Par1_1 bit 1 1 NO Par1_2 bit 1 1 NO Par1_3 bit 1 1 NO Par1_3_1bit 1 1 NO Par1_3_2 bit 1 1 NO Par1_3_3 bit 1 1 NO Par1_3_4 bit 1 1 NOPar1_3_5 bit 1 1 NO Par1_4 bit 1 1 NO Par2_1 bit 1 1 NO Par2_1_1 bit 1 1NO Par2_1_2 bit 1 1 NO

[0160] Database Table Column DataType Length Precision Null Par2_1_3 bit1 1 NO Par2_1_4 bit 1 1 NO Par2_1_5 bit 1 1 NO Par2_1_6 bit 1 1 NOPar2_1_7 bit 1 1 NO Par2_1_8 bit 1 1 NO Par2_2 bit 1 1 NO Par2_3 bit 1 1NO Par3_1 bit 1 1 NO Par3_2 bit 1 1 NO Par3_3 bit 1 1 NO Par3_4 bit 1 1NO Par6_4_1 bit 1 1 NO Par6_4_2 bit 1 1 NO Par6_4_3 bit 1 1 NO Par6_4_4bit 1 1 NO Par6_4_5 bit 1 1 NO Par6_4_6 bit 1 1 NO Par6_4_7 bit 1 1 NOPar6_4_8 bit 1 1 NO Par6_4_9 bit 1 1 NO Par4_1 bit 1 1 NO Par4_2 bit 1 1NO Par4_3 bit 1 1 NO Par4_4 bit 1 1 NO Par4_5 bit 1 1 NO Par4_5_1 bit 11 NO Par4_5_2 bit 1 1 NO Par4_6 bit 1 1 NO Par4_7 bit 1 1 NO Par4_8 bit1 1 NO Par5_1 bit 1 1 NO Par5_1_1 bit 1 1 NO Par5_1_2 bit 1 1 NOPar5_1_3 bit 1 1 NO Par5_1_4 bit 1 1 NO Par5_1_5 bit 1 1 NO

[0161] Database Table Column DataType Length Precision Null Par5_1_6 bit1 1 NO Par5_2 bit 1 1 NO Par5_2_1 bit 1 1 NO Par5_2_2 bit 1 1 NO Par5_3bit 1 1 NO Par5_4 bit 1 1 NO Par5_5 bit 1 1 NO Par6_1 bit 1 1 NOPar6_1_1 bit 1 1 NO Par6_1_2 bit 1 1 NO Par6_1_3 bit 1 1 NO Par6_1_4 bit1 1 NO Par6_2 bit 1 1 NO Par6_3 bit 1 1 NO Par6_4 bit 1 1 NO Par6_5 bit1 1 NO Sec1_0 bit 1 1 NO Sec2_0 bit 1 1 NO Sec3_0 bit 1 1 NO Sec4_0 bit1 1 NO Sec5_0 bit 1 1 NO Sec6_0 bit 1 1 NO SSAA bit 1 1 NO AppenD_0 bit1 1 NO AppenD_1 bit 1 1 NO AppenD_3 bit 1 1 NO AppenD_5 bit 1 1 NOAppenE_0 bit 1 1 NO AppenE_1 bit 1 1 NO AppenE_3 bit 1 1 NO AppenE_5 bit1 1 NO AppenF_1 bit 1 1 NO AppenF_5 bit 1 1 NO AppenG_1 bit 1 1 NOAppenG_2 bit 1 1 NO AppenG_6 bit 1 1 NO AppenH_1 bit 1 1 NO

[0162] Database Table Column DataType Length Precision Null AppenH_3 bit1 1 NO AppenH_5 bit 1 1 NO AppenI_1 bit 1 1 NO AppenI_3 bit 1 1 NOAppenI_5 bit 1 1 NO AppenJ_0 bit 1 1 NO AppenJ_1 bit 1 1 NO AppenJ_3 bit1 1 NO AppenJ_5 bit 1 1 NO AppenK_0 bit 1 1 NO AppenK_1 bit 1 1 NOAppenK_3 bit 1 1 NO AppenK_5 bit 1 1 NO AppenL_0 bit 1 1 NO AppenL_1 bit1 1 NO AppenL_3 bit 1 1 NO AppenL_5 bit 1 1 NO AppenM_0 bit 1 1 NOAppenM_1 bit 1 1 NO AppenM_3 bit 1 1 NO AppenM_5 bit 1 1 NO AppenN_0 bit1 1 NO AppenN_1 bit 1 1 NO AppenN_3 bit 1 1 NO AppenN_5 bit 1 1 NOAppenO_0 bit 1 1 NO AppenO_1 bit 1 1 NO AppenO_3 bit 1 1 NO AppenO_5 bit1 1 NO AppenP_1 bit 1 1 NO AppenP_3 bit 1 1 NO AppenP_5 bit 1 1 NOAppenQ_1 bit 1 1 NO AppenQ_2 bit 1 1 NO AppenQ_6 bit 1 1 NO AppenR_0 bit1 1 NO AppenR_1 bit 1 1 NO

[0163] Database Table Column DataType Length Precision Null AppenR_3 bit1 1 NO AppenR_5 bit 1 1 NO Par3_5 bit 1 1 NO SSAATemplate Paragraph97varchar 255 0 YES Instance int 4 10 YES Text text 16 0 YES Notes varchar50 0 YES Document varchar 50 0 YES Service varchar 50 0 YES Commandvarchar 50 0 YES Paragraph varchar 255 0 YES SystemUserCategory Categoryvarchar 50 0 NO Type char 1 0 YES SystemUsers PID decimal 9 18 NOCategory varchar 50 0 NO MinClearance varchar 50 0 NO AISCertLevelvarchar 50 0 YES ForeignNational varchar 50 0 YES Description text 16 0YES CatID int 4 10 NO Rank int 4 10 NO Tasks PID decimal 9 18 NO TaskIDint 4 10 NO Title varchar 50 0 YES Date varchar 50 0 YES Milestone text16 0 YES NewDate datetime 8 23 YES TestingStatus PID decimal 9 18 NOBaselineGenerated bit 1 1 NO TestCustomized bit 1 1 NO UDTAdded bit 1 1NO

[0164] Database Table Column DataType Length Precision NullAppendixGLeadinData bit 1 1 NO AppendixHLeadinData bit 1 1 NOTestResultsLookup Rank int 4 10 YES Result varchar 50 0 YES ThreatLookUpCategoryRank int 4 10 NO Rank int 4 10 NO ThreatCategory varchar 50 0 NOThreatElement varchar 50 0 NO TrainingLookup Rank int 4 10 YESTrainingLevel varchar 50 0 YES WebCALookups WebcaLookupsId int 4 10 NOTableName varchar 50 0 NO ColumnName varchar 50 0 NO Description varchar50 0 YES Size int 4 10 YES

[0165] The many features and advantages of the invention are apparentfrom the detailed specification, and thus, it is intended by theappended claims to cover all such features and advantages of theinvention which fall within the true spirit and scope of the invention.Further, since numerous modifications and variations will readily occurto those skilled in the art, it is not desired to limit the invention tothe exact construction and operation illustrated and described, andaccordingly, all suitable modifications and equivalents may be resortedto, falling within the scope of the invention. While the foregoinginvention has been described in detail by way of illustration andexample of preferred embodiments, numerous modifications, substitutions,and alterations are possible without departing from the scope of theinvention defined in the following claims.

Having thus described our invention, what we claim as new and desire tosecure by letters patent is as follows:
 1. A computer-assisted method ofassessing the risk of and/or determining the suitability of a targetsystem to comply with at least one predefined standard, regulationand/or requirement, the target system including hardware and/orsoftware, the method comprising the steps of: a) collecting informationdescriptive of at least one aspect of the target system hardware and/orsoftware, and/or a physical environment in which the system operates; b)selecting at least one predefined standard, regulation and/orrequirement with which the system is to comply; c) generating a scorefor each of a plurality of threat elements, each score indicating alikelihood of that threat element affecting and/or impacting the targetsystem; d) selecting at least one test procedure against which thesystem is tested to satisfy the at least one predefined standard,regulation and/or requirement; e) performing the steps associated withsaid at least one test procedure in said step d) to determine whetherthe target system passes or fails said at least one the test procedure;and f) (1) obtaining a threat correlation indication associated withsaid at least one test procedure, wherein said threat correlationindication indicates a relative potential of one or more given threatsto exploit a vulnerability caused by a failure of said at least one testprocedure, and (2) determining a risk assessment by comparing each scoregenerated in said step c) with a corresponding threat correlationindication of said step f) (1).
 2. The method according to claim 1wherein the information collected in said step a) comprises at least oneof central processing unit (CPU) manufacturer, CPU clock speed,operating system (OS) manufacturer, OS version, and OS patches.
 3. Themethod according to claim 1 wherein said selecting step b) is initiallyperformed by the computer.
 4. The method according to claim 3, furthercomprising the step of enabling a user to optionally input at least onestandard, regulation and/or requirement.
 5. The method according toclaim 3, further comprising the step of enabling a user to optionallyedit at least one standard, regulation and/or requirement.
 6. The methodaccording to claim 1 wherein said scores for said step c) comprise atleast one of: a) negligible, wherein negligible indicates that thethreat element is not applicable or has negligible likelihood ofoccurrence; b) low, wherein low indicates that the threat element has arelatively low likelihood of occurrence; c) medium, wherein mediumindicates that the threat element has a medium likelihood of occurrence;and d) high, wherein high indicates that the threat element has arelatively high likelihood of occurrence.
 7. The method according toclaim 1 wherein said score of said step c) is generated in response toone or more user provided inputs.
 8. The method according to claim 7wherein the user can modify and/or edit said score as determined in saidstep c).
 9. The method according to claim 1 wherein said step c) threatelements comprise at least one of natural disaster elements, systemfailure elements, environmental failure elements, unintentional humanelements, and intentional human elements.
 10. The method according toclaim 9 wherein the natural disaster threat elements comprise at leastone of fire, flood, earthquake, volcano, tornado and lighting elements.11. The method according to claim 9 wherein the system failure threatelements comprise at least one of a hardware failure, a power failure,and a communication link failure.
 12. The method according to claim 9wherein the environmental failure threat elements comprise at least oneof temperature, power, humidity, sand, dust, shock, and vibration. 13.The method according to claim 9 wherein the human unintentional threatelement comprises at least one of a software design error, a systemdesign error, and an operator error.
 14. The method according to claim 9wherein the human intentional threat elements comprise at least one ofan authorized system administrator, an authorized maintenance personnel,an authorized user, a terrorist, a hacker, a saboteur, a thief, and avandal.
 15. The method according to claim 1 wherein said step f) threatcorrelation indication comprises at least one of the following scores:a) negligible, wherein negligible indicates that the threat is notapplicable to the vulnerability; b) low, wherein low indicates that thethreat has a low potential to exploit the vulnerability; c) medium,wherein medium indicates that the threat has a potential to exploit thevulnerability; and d) high, wherein high indicates that the threat has arelatively high potential to exploit the vulnerability.
 16. The methodaccording to claim 15 wherein the risk assessment in said step f) isdetermined in accordance with the following steps: a) for each elementin the project threat profile and corresponding element in the threatcorrelation pattern: 1) if a threat element as determined in said stepc) is negligible and a corresponding element in the threat correlationindication as determined in said step f) is anything, then the overallrisk of the element is negligible; 2) if a threat element as determinedin said step c) is low and the corresponding element in the threatcorrelation indication as determined in said step f) is negligible, thenthe overall risk of the element is low; 3) if a threat element asdetermined in said step c) is low and the corresponding element in thethreat correlation indication as determined in said step f) is low, thenthe overall risk of the element is low; 4) if a threat element asdetermined in said step c) is low and the corresponding element in thethreat correlation indication as determined in said step f) is medium,then the overall risk of the element is low; 5) if a threat element asdetermined in said step c) is low and the corresponding element in thethreat correlation indication as determined in said step f) is high,then the overall risk of the element is medium; 6) if a threat elementas determined in said step c) is medium and the corresponding element inthe threat correlation indication as determined in said step f) isnegligible, then the overall risk of the element is negligible; 7) if athreat element as determined in said step c) is medium and thecorresponding element in the threat correlation indication as determinedin said step f) is low, then the overall risk of the element is low; 8)if a threat element as determined in said step c) is medium and thecorresponding element in the threat correlation indication as determinedin said step f) is medium, then the overall risk of the element ismedium; 9) if a threat element as determined in said step c) is mediumand the corresponding element in the threat correlation indication asdetermined in said step f) is high, then the overall risk of the elementis medium; 10) if a threat element as determined in said step c) is highand the corresponding element in the threat correlation indication asdetermined in said step f) is negligible, then the overall risk of theelement is negligible; 11) if a threat element as determined in saidstep c) is high and the corresponding element in the threat correlationindication as determined in said step f) is low, then the overall riskof the element is medium; 12) if a threat element as determined in saidstep c) is high and the corresponding element in the threat correlationindication as determined in said step f) is medium, then the overallrisk of the element is high; and 13) if a threat element as determinedin said step c) is high and the corresponding element in the threatcorrelation indication as determined in said step f) is high, then theoverall risk of the element is high; and b) selecting the risk profilefor the failed test procedure as being the highest overall risk element.17. The method according to claim 16, further comprising the step ofdetermining an overall system risk.
 18. The method according to claim 17wherein the overall system risk is the highest overall risk element ofeach of one or more failed test procedures.
 19. The method according toclaim 17, further comprising the step of printing a documentationpackage that will enable a determination to be made whether the testsystem complies with the at least one predefined standard, regulationand/or requirement selected in said step b).
 20. The method according toclaim 19 wherein the documentation package includes a risk assessmentfor at least one failed test procedure.
 21. The method according toclaim 19 wherein the documentation package includes an overall systemrisk.
 22. In a general purpose computing system, a computer-assisted anduser assisted method for assessing the risk of and/or determining thesuitability of a target system to comply with at least one predefinedstandard, regulation and/or requirement, the target system includinghardware and/or software, the general purpose computing systeminteracting with a user and performing the steps of: a) collectingand/or receiving information descriptive of at least one aspect of thetarget system hardware and/or software, and/or a physical environment inwhich the system operates; b) selecting at least one predefinedstandard, regulation and/or requirement with which the system is tocomply; c) generating a score for each of a plurality of threatelements, each score indicating a likelihood of that threat elementaffecting and/or impacting the target system; d) selecting at least onetest procedure against which the target system is tested to satisfy theat least one predefined standard, regulation and/or requirement; e)performing the steps associated with said at least one test procedure insaid step d) to determine whether the target system passes or fails saidat least one the test procedure; and f) (1) obtaining a threatcorrelation indication associated with said at least one test procedure,wherein said threat correlation indication indicates a relativepotential of one or more given threats to exploit a vulnerability causedby a failure of said at least one test procedure, and (2) determining arisk assessment by comparing each score generated in said step c) with acorresponding threat correlation indication of said step f) (1).
 23. Thegeneral purpose computing system according to claim 22 wherein theinformation collected in said step a) comprises at least one of centralprocessing unit (CPU) manufacturer, CPU clock speed, operating system(OS) manufacturer, OS version, and OS patches.
 24. The general purposecomputing system according to claim 23, wherein the user can optionallyinput at least one standard, regulation and/or requirement.
 25. Thegeneral purpose computing system according to claim 23, wherein the usercan optionally edit at least one standard, regulation and/orrequirement.
 26. The general purpose computing system according to claim22 wherein said scores for said step c) comprise at least one of: a)negligible, wherein negligible indicates that the threat element is notapplicable or has negligible likelihood of occurrence; b) low, whereinlow indicates that the threat element has a relatively low likelihood ofoccurrence; c) medium, wherein medium indicates that the threat elementhas a medium likelihood of occurrence; and d) high, wherein highindicates that the threat element has a relatively high likelihood ofoccurrence.
 27. The general purpose computing system according to claim22 wherein said score of said step c) is generated in response to one ormore user provided inputs.
 28. The general purpose computing systemaccording to claim 27 wherein the user can modify and/or edit said scoreas determined in said step c).
 29. The general purpose computing systemaccording to claim 22 wherein said step c) threat elements comprise atleast one of natural disaster elements, system failure elements,environmental failure elements, unintentional human elements, andintentional human elements.
 30. The general purpose computing systemaccording to claim 29 wherein the natural disaster threat elementscomprise at least one of fire, flood, earthquake, volcano, tornado andlighting elements.
 31. The general purpose computing system according toclaim 29 wherein the system failure threat elements comprise at leastone of a hardware failure, a power failure, and a communication linkfailure.
 32. The general purpose computing system according to claim 29wherein the environmental failure threat elements comprise at least oneof temperature, power, humidity, sand, dust, shock, and vibration. 33.The general purpose computing system according to claim 29 wherein thehuman unintentional threat element comprises at least one of a softwaredesign error, a system design error, and an operator error.
 34. Thegeneral purpose computing system according to claim 29 wherein the humanintentional threat elements comprise at least one of an authorizedsystem administrator, an authorized maintenance personnel, an authorizeduser, a terrorist, a hacker, a saboteur, a thief, and a vandal.
 35. Thegeneral purpose computing system according to claim 22 wherein said stepf) threat correlation indication comprises at least one of the followingscores: a) negligible, wherein negligible indicates that the threatelement is not applicable to the vulnerability; b) low, wherein lowindicates that the threat element has a low potential to exploit thevulnerability; c) medium, wherein medium indicates that the threatelement has a potential to exploit the vulnerability; and d) high,wherein high indicates that the threat element has a relatively highpotential to exploit the vulnerability.
 36. The general purposecomputing system according to claim 35 wherein the risk assessment insaid step f) is determined in accordance with the following steps: a)for each element in the project threat profile and corresponding elementin the threat correlation pattern: 1) if a threat element as determinedin said step c) is negligible and a corresponding element in the threatcorrelation indication as determined in said step f) is anything, thenthe overall risk of the element is negligible; 2) if a threat element asdetermined in said step c) is low and the corresponding element in thethreat correlation indication as determined in said step f) isnegligible, then the overall risk of the element is low; 3) if a threatelement as determined in said step c) is low and the correspondingelement in the threat correlation indication as determined in said stepf) is low, then the overall risk of the element is low; 4) if a threatelement as determined in said step c) is low and the correspondingelement in the threat correlation indication as determined in said stepf) is medium, then the overall risk of the element is low; 5) if athreat element as determined in said step c) is low and thecorresponding element in the threat correlation indication as determinedin said step f) is high, then the overall risk of the element is medium;6) if a threat element as determined in said step c) is medium and thecorresponding element in the threat correlation indication as determinedin said step f) is negligible, then the overall risk of the element isnegligible; 7) if a threat element as determined in said step c) ismedium and the corresponding element in the threat correlationindication as determined in said step f) is low, then the overall riskof the element is low; 8) if a threat element as determined in said stepc) is medium and the corresponding element in the threat correlationindication as determined in said step f) is medium, then the overallrisk of the element is medium; 9) if a threat element as determined insaid step c) is medium and the corresponding element in the threatcorrelation indication as determined in said step f) is high, then theoverall risk of the element is medium; 10) if a threat element asdetermined in said step c) is high and the corresponding element in thethreat correlation indication as determined in said step f) isnegligible, then the overall risk of the element is negligible; 11) if athreat element as determined in said step c) is high and thecorresponding element in the threat correlation indication as determinedin said step f) is low, then the overall risk of the element is medium;12) if a threat element as determined in said step c) is high and thecorresponding element in the threat correlation indication as determinedin said step f) is medium, then the overall risk of the element is high;and 13) if a threat element as determined in said step c) is high andthe corresponding element in the threat correlation indication asdetermined in said step f) is high, then the overall risk of the elementis high; and b) selecting the risk profile for the failed test procedureas being the highest overall risk element.
 37. The general purposecomputing system according to claim 36, further comprising the step ofdetermining an overall system risk.
 38. The general purpose computingsystem according to claim 37 wherein the overall system risk is thehighest overall risk element of each of one or more failed testprocedures.
 39. The general purpose computing system according to claim37, wherein the general purpose computing system prints a documentationpackage that will enable a determination to be made whether the testsystem complies with the at least one predefined standard, regulationand/or requirement selected in said step b).
 40. The general purposecomputing system according to claim 39 wherein the documentation packageincludes a risk assessment for at least one failed test procedure. 41.The general purpose computing system according to claim 39 wherein thedocumentation package includes an overall system risk.
 42. A computerprogram medium storing computer instructions therein for instructing acomputer to perform a computer-implemented and user assisted process forassessing the risk of and/or determining the suitability of a targetsystem to comply with at least one predefined standard, regulationand/or requirement, the target system including hardware and/orsoftware, the program medium comprising: a recording medium readable bythe computer; and the computer instructions stored on said recordingmedium instructing the computer to perform the computer-implemented anduser assisted process, the instructions including: a) collecting and/orreceiving information descriptive of at least one aspect of the targetsystem hardware and/or software, and/or a physical environment in whichthe system operates; b) selecting at least one predefined standard,regulation and/or requirement with which the system is to comply; c)generating a score for each of a plurality of threat elements, eachscore indicating a likelihood of that threat elements affecting and/orimpacting the system; d) selecting at least one test procedure againstwhich the system is tested to satisfy the at least one predefinedstandard, regulation and/or requirement; e) performing the stepsassociated with said at least one test procedure in said step d) todetermine whether the target system passes or fails said at least onethe test procedure; and f) (1) obtaining a threat correlation indicationassociated with said at least one test procedure, wherein said threatcorrelation indication indicates a relative potential of one or moregiven threats to exploit a vulnerability caused by a failure of said atleast one test procedure, and (2) determining a risk assessment bycomparing each threat element generated in said step c) with said threatcorrelation indication of said step f)(1).
 43. The computer programmedium according to claim 42 wherein the information collected in saidinstruction a) comprises at least one of central processing unit (CPU)manufacturer, CPU clock speed, operating system (OS) manufacturer, OSversion, and OS patches.
 44. The computer program medium according toclaim 43, further comprising instructions that enable the user tooptionally input at least one standard, regulation and/or requirement.45. The computer program medium according to claim 43, furthercomprising instructions that enable the user to optionally edit at leastone standard, regulation and/or requirement.
 46. The computer programmedium according to claim 42 wherein said scores for said step c)comprise at least one of: a) negligible, wherein negligible indicatesthat the threat element is not applicable or has negligible likelihoodof occurrence; b) low, wherein low indicates that the threat element hasa relatively low likelihood of occurrence; c) medium, wherein mediumindicates that the threat element has a medium likelihood of occurrence;and d) high, wherein high indicates that the threat element has arelatively high likelihood of occurrence.
 47. The computer programmedium according to claim 42 wherein said score of said step c) isgenerated in response to one or more user provided inputs.
 48. Thecomputer program medium according to claim 47 wherein the user canmodify and/or edit said score as determined in said step c).
 49. Thecomputer program medium according to claim 42 wherein said instructionc) threat elements comprise at least one of natural disaster elements,system failure elements, environmental failure elements, unintentionalhuman elements, and intentional human elements.
 50. The computer programmedium according to claim 49 wherein the natural disaster threatelements comprise at least one of fire, flood, earthquake, volcano,tornado and lighting elements.
 51. The computer program medium accordingto claim 49 wherein the system failure threat elements comprise at leastone of a hardware failure, a power failure, and a communication linkfailure.
 52. The computer program medium according to claim 49 whereinthe environmental failure threat elements comprise at least one oftemperature, power, humidity, sand, dust, shock, and vibration.
 53. Thecomputer program medium according to claim 49 wherein the humanunintentional threat elements comprise at least one of a software designerror, a system design error, and an operator error.
 54. The computerprogram medium according to claim 49 wherein the human intentionalthreat elements comprise at least one of an authorized systemadministrator, an authorized maintenance personnel, an authorized user,a terrorist, a hacker, a saboteur, a thief, and a vandal.
 55. Thecomputer program medium according to claim 42 wherein said instructionf) threat correlation indication comprises at least one of the followingscores: a) negligible, wherein negligible indicates that the threatelement is not applicable to the vulnerability; b) low, wherein lowindicates that the threat element has a low potential to exploit thevulnerability; c) medium, wherein medium indicates that the threatelement has a potential to exploit the vulnerability; and d) high,wherein high indicates that the threat element has a relatively highpotential to exploit the vulnerability.
 56. The computer program mediumaccording to claim 55 wherein the risk profile in said instruction f) isdetermined in accordance with the following steps: a) for each elementin the project threat profile and corresponding element in the threatcorrelation pattern: 1) if a threat element as determined in said stepc) is negligible and a corresponding element in the threat correlationindication as determined in said step f) is anything, then the overallrisk of the element is negligible; 2) if a threat element as determinedin said step c) is low and the corresponding element in the threatcorrelation indication as determined in said step f) is negligible, thenthe overall risk of the element is low; 3) if a threat element asdetermined in said step c) is low and the corresponding element in thethreat correlation indication as determined in said step f) is low, thenthe overall risk of the element is low; 4) if a threat element asdetermined in said step c) is low and the corresponding element in thethreat correlation indication as determined in said step f) is medium,then the overall risk of the element is low; 5) if a threat element asdetermined in said step c) is low and the corresponding element in thethreat correlation indication as determined in said step f) is high,then the overall risk of the element is medium; 6) if a threat elementas determined in said step c) is medium and the corresponding element inthe threat correlation indication as determined in said step f) isnegligible, then the overall risk of the element is negligible; 7) if athreat element as determined in said step c) is medium and thecorresponding element in the threat correlation indication as determinedin said step f) is low, then the overall risk of the element is low; 8)if a threat element as determined in said step c) is medium and thecorresponding element in the threat correlation indication as determinedin said step f) is medium, then the overall risk of the element ismedium; 9) if a threat element as determined in said step c) is mediumand the corresponding element in the threat correlation indication asdetermined in said step f) is high, then the overall risk of the elementis medium; 10) if a threat element as determined in said step c) is highand the corresponding element in the threat correlation indication asdetermined in said step f) is negligible, then the overall risk of theelement is negligible; 11) if a threat element as determined in saidstep c) is high and the corresponding element in the threat correlationindication as determined in said step f) is low, then the overall riskof the element is medium; 12) if a threat element as determined in saidstep c) is high and the corresponding element in the threat correlationindication as determined in said step f) is medium, then the overallrisk of the element is high; and 13) if a threat element as determinedin said step c) is high and the corresponding element in the threatcorrelation indication as determined in said step f) is high, then theoverall risk of the element is high; and b) selecting the risk profilefor the failed test procedure as being the highest overall risk element.57. The computer program medium according to claim 56, furthercomprising instructions for determining an overall system risk.
 58. Thecomputer program medium according to claim 57 wherein the overall systemrisk is the highest overall risk element of each of one or more failedtest procedures.
 59. The computer program medium according to claim 57,further comprising instructions for generating and printing adocumentation package that will enable a determination to be madewhether the test system complies with the at least one predefinedstandard, regulation and/or requirement.
 60. The computer program mediumaccording to claim 59 wherein the documentation package includes a riskassessment for at least one failed test procedure.
 61. The computerprogram medium according to claim 59 wherein the documentation packageincludes an overall system risk.